feat(mcp): surface 'serverInfo' exposed from the MCP server#14288
Merged
aayush-kapoor merged 2 commits intomainfrom Apr 10, 2026
Merged
feat(mcp): surface 'serverInfo' exposed from the MCP server#14288aayush-kapoor merged 2 commits intomainfrom
aayush-kapoor merged 2 commits intomainfrom
Conversation
4 tasks
lgrammel
approved these changes
Apr 10, 2026
vercel-ai-sdk bot
pushed a commit
that referenced
this pull request
Apr 10, 2026
## Background introduced in #13825 we used to capture the `serverInfo` in the schema but never surface it through to the client. only `result.capabilities` was stored and `result.serverInfo` was thrown away. there was no field on the client to hold it and no property on the MCPClient interface to access it ## Summary - added `title` field to `ClientOrServerImplementationSchema` to align with [MCP spec](https://modelcontextprotocol.io/specification/2025-11-25/schema#implementation) - exposed `serverInfo` via a getter function ## Manual Verification verified by running the client and server under `examples/mcp/src/server-info` ## Checklist - [x] Tests have been added / updated (for bug fixes / features) - [ ] Documentation has been added / updated (for bug fixes / features) - [x] A _patch_ changeset for relevant packages has been added (for bug fixes / features - run `pnpm changeset` in the project root) - [x] I have reviewed this pull request (self-review)
Contributor
|
✅ Backport PR created: #14321 |
vercel-ai-sdk bot
added a commit
that referenced
this pull request
Apr 10, 2026
…#14321) This is an automated backport of #14288 to the release-v6.0 branch. FYI @aayush-kapoor Co-authored-by: Aayush Kapoor <83492835+aayush-kapoor@users.noreply.github.com>
Contributor
|
🚀 Published in:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Background
introduced in #13825
we used to capture the
serverInfoin the schema but never surface it through to the client. onlyresult.capabilitieswas stored andresult.serverInfowas thrown away. there was no field on the client to hold it and no property on the MCPClient interface to access itSummary
titlefield toClientOrServerImplementationSchemato align with MCP specserverInfovia a getter functionManual Verification
verified by running the client and server under
examples/mcp/src/server-infoChecklist
pnpm changesetin the project root)